home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
faq
/
news
/
inn_faq
/
diff2
< prev
next >
Wrap
Internet Message Format
|
1994-04-05
|
11KB
Path: bloom-beacon.mit.edu!hookup!swrinde!cs.utexas.edu!uunet!news.mentorg.com!sdl!not-for-mail
From: tal@Warren.MENTORG.COM (Tom Limoncelli)
Newsgroups: news.software.nntp,news.software.b,news.answers
Subject: Changes to INN FAQ Part 2/4: Debugging Guide & Tutorial
Supersedes: <inn-faq-changes-2-765518416@Warren.MENTORG.COM>
Followup-To: news.software.nntp
Date: 5 Apr 1994 11:34:54 -0400
Organization: Mentor Graphics - IC Group, Warren, NJ, USA
Lines: 262
Sender: tal@Warren.MENTORG.COM
Approved: news-answers-request@MIT.Edu
Distribution: world
Expires: 04/20/94
Message-ID: <inn-faq-changes-2-764139608@Warren.MENTORG.COM>
References: <inn-faq-changes-1-764139608@Warren.MENTORG.COM>
Reply-To: Tom_Limoncelli@Warren.MENTORG.COM (Tom Limoncelli)
NNTP-Posting-Host: sdl.warren.mentorg.com
Xref: bloom-beacon.mit.edu news.software.nntp:5494 news.software.b:4176 news.answers:17711
Posted-By: auto-faq 2.4
Archive-name: inn-faq/diff2
[ There was a problem with the 'diff' shell script I was
using. Diffs haven't been properly posted here since
the beginning of the year (maybe longer). So, here are
the diffs since Jan 1. ]
*** 1.13 1994/01/17 14:32:59
--- FAQ-inn.2 1994/03/31 21:21:59
***************
*** 1,4 ****
! Last Changed: $Id: FAQ-inn.2,v 1.13 1994/01/17 14:32:59 tal Exp $
Part 2 of 4
--- 1,4 ----
! Last Changed: $Id: FAQ-inn.2,v 1.25 1994/03/31 21:21:56 tal Exp $
Part 2 of 4
***************
*** 25,30 ****
--- 25,31 ----
syslog message: ME internal no control and/or junk group
syslog message: Can't setup communication (bind failure)
syslog message: ME bad_newsfeeds no feeding sites
+ syslog message: ME cant GetConfigValue
THE DEBUGGING TUTORIAL:
Should I read the Install.ms file in its entirety
before reading this document?
***************
*** 42,47 ****
--- 43,49 ----
How does the "ME" line interact with the other lines?
Cookbook example of an outgoing NNTP feed.
Cookbook example of an outgoing UUCP feed.
+ Cookbook example of an outgoing UUCP-over-TCP feed.
Testing an outgoing feed (your "newsfeeds" configuration).
Other cron jobs.
Cookbook example setting up NOV ("overchan").
***************
*** 48,53 ****
--- 50,56 ----
How do I use nntplink with INN?
How do I use newsgate with INN?
OTHER ERROR MESSAGES AND WHAT THEY MEAN:
+ ld.so: Undefined symbol: _dbzwritethrough
Why does my innd often die with the message "Can't sync history..."
syslog message: ME cant sendto CCreader bytes 4 No such file
or directory.
***************
*** 57,62 ****
--- 60,68 ----
"cant fopen <newsgroup>/.thread No such file or directory"
news.daily reports: "Expire had problems removing articles"
syslog: ME cant nonblock 15 Operation not supported.
+ innd: ME cant update_active control
+ syslog message: innxmit[1234]: max connect failed Error 0
+ Can't open "/usr/local/news/shlock955", Permission denied
=====================================================================
***************
*** 126,131 ****
--- 132,152 ----
dummy-feed:!*::
+ ------------------------------
+
+ Subject: syslog message: ME cant GetConfigValue
+
+ Jan 12 17:38:06 galaxy innd: ME cant GetConfigValue pathhost Error 0
+ ^^^^^^^^
+
+ This means you don't have "pathhost:" in your inn.conf.
+
+ GetConfigValue is the routine that gets data out of the inn.conf file.
+ If you get the above error, it means you don't have a particular value
+ in your inn.conf. Run "inncheck -v" usually will tell you what you
+ need to do.
+
+
=====================================================================
THE DEBUGGING TUTORIAL
(or, What do I do after Install.ms?)
***************
*** 883,888 ****
--- 904,966 ----
------------------------------
+ Subject: Cookbook example of an outgoing UUCP-over-TCP feed:
+
+ jerry@strobe.ATC.Olivetti.Com (Jerry Aguirre) writes:
+
+ People ask about this like it was something exotic requiring special
+ setup. Kind of like: "I know how to use a wheel barrow and I know how
+ to shovel sand but how do I shovel sand in a wheel barrow?"
+
+ Step 1: Set up a UUCP/TCP connection between you and the destination
+ site. How? Read your UUCP documentation. If your, and the
+ desitination's, UUCP supports UUCP/TCP then it will be documented. If
+ not then get a better version of UUCP.
+
+ The point is to get the UUCP/TCP link working before even thinking
+ about sending news over it. This is true of any news feed over UUCP;
+ even dialup. Try using "uucp" to copy some scratch file to the other
+ end. When you have that working then you are ready for the next step.
+
+ The only "gotcha" here that I can think of is that the destination host
+ may not be accepting UUCP/TCP connections. Before wasting your time
+ trying to debug do a "telnet destination.host.name uucp" and see what
+ happens. If the connection is accepted and you see a "login" banner
+ then it is ready for you. If not then ask the admin of that site to
+ enable UUCP/TCP. This is typically done by uncommenting it in
+ /etc/inetd.conf and -HUPing inetd (on REAL versions of Unix).
+
+ Step 2. Set up a standard compressed news feed to the UUCP name of the
+ destination site. How? Read your news documentation. Setting up UUCP
+ feeds is a standard, documented, procedure. In this FAQ you'll find it
+ in "Cookbook example of an outgoing UUCP feed". Doing compression is
+ nothing special, it's part of the procedure you would be doing anyway.
+ It's either a flag or a slighly different command. The news system has
+ NO knowledge that this is UUCP/TCP. For all it knows this is a
+ standard dialup connection. In fact is is possible to have the UUCP
+ connection fall back to dialup if the TCP connection fails. The news
+ batching software just doesn't care.
+
+ The only variation here I can think of is to make the batch size bigger
+ than the default. The 50K default was picked back in the days when
+ modems were 1200 BPS (or even 300). It is no longer appropriate for
+ todays 9600 BPS or faster connections. Using a bigger batch size cuts
+ down on dead time in the connection and lets compress do a better job.
+ I would go to at least 200K batches.
+
+ Now maybe it would be nice to have a "cookbook", step by step, set of
+ instructions on how to do this. But UUCP seems to vary a bit between
+ different versions so what might work at one place would be useless at
+ another. And setting up the news feed is going to be different between
+ the different versions of news (B, C, and INN).
+
+ I suggest that if people are having trouble setting up a UUCP/TCP
+ connection that they post their configuration to the net and ask how it
+ is done on their versions of Unix and UUCP.
+
+
+ ------------------------------
+
Subject: Testing an outgoing feed (your "newsfeeds" configuration).
Here is a decent game-plan for testing your newsfeeds configuration:
***************
*** 963,969 ****
Step 6: (optional) To create the original database:
(run this as "news")
! % /usr/local/news/bin/expireover -a -s
If you skip this step, access will be slow for articles that came
in before you started "overchan". This is not a problem. You
--- 1041,1048 ----
Step 6: (optional) To create the original database:
(run this as "news")
! % /usr/local/news/bin/expireover -a
! % /usr/local/news/bin/expireover -s
If you skip this step, access will be slow for articles that came
in before you started "overchan". This is not a problem. You
***************
*** 1072,1077 ****
--- 1151,1175 ----
------------------------------
+ Subject: ld.so: Undefined symbol: _dbzwritethrough
+
+ > Everything compiles correctly, but when I try to test rc.local I get:
+ >
+ > hermes# sh /usr/local/etc/rc.news
+ > ld.so: Undefined symbol: _dbzwritethrough
+ >
+ > What am I doing wrong?
+
+ This means that you are using a $INN/lib/dbz.c file that hasn't been
+ patched with the $INN/lib/dbz.pch patch. Apply that patch file to
+ dbz.c and rebuild libinn.a et al. and things should be copacetic. See
+ section "5.2 The DBZ package" of the Install.ms document. This might
+ have happened if you don't have the "patch" program (available from any
+ FSF/GNU archive).
+
+
+ ------------------------------
+
Subject: Why does my innd often die with the message "Can't sync history,
interrupted system call"
***************
*** 1166,1171 ****
--- 1264,1275 ----
ctlinnd renumber ''
to get things synchronized again.
+ If your history file is corrupt, you should do:
+ ctlinnd renumber ''
+ makehistory -buv
+ ctlinnd renumber ''
+ (Note: the "makehistory" will take hours to run.)
+
------------------------------
***************
*** 1238,1240 ****
--- 1342,1384 ----
ignore it.
+ ------------------------------
+
+ Subject: innd: ME cant update_active control
+
+ What does "innd: ME cant update_active control" mean?
+
+ Look at your active file. One of the fields is "99999" and has to be
+ incremented to "100000" but there is no space. Shut down innd
+ ("ctlinnd shutdown x"). Edit your active file to add more leading
+ zero's to all the numbers. Restart innd.
+
+
+ ------------------------------
+
+ Subject: syslog message: innxmit[1234]: max connect failed Error 0
+
+ John Line <jml4@cus.cam.ac.uk> writes:
+
+ If you get syslog messages like "innxmit[1234]: max connect failed
+ Error 0" when using nntpsend, it probably means you messed up a line in
+ nntpsend.ctl (specifically, missed out one of the first two fields).
+ While nntpsend.ctl is an obvious place to look for an nntpsend problem,
+ there is nothing obvious to link the error message directly to the
+ problem, because the text "max" is actually something invented by
+ nntpsend when processing the file, and doesn't exist in nntpsend.ctl.
+ It means the next-to-last field was null, but was the second field when
+ it should have been the third!
+
+ NB Remember to try inncheck when you have problems like this. I only
+ just thought of it, after finding the problem the hard way, and it
+ immediately reported "nntpsend.ctl:18: malformed line."
+
+
+ ------------------------------
+
+ Subject: Can't open "/usr/local/news/shlock955", Permission denied
+
+ This usually means you don't have /usr/local/news owned by "news". The
+ first time you run "make install" it should set the proper ownership if
+ you run "make install" as "root".